-
Notifications
You must be signed in to change notification settings - Fork 781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[flash_ctrl] Enable firmware dealing with multi-bit ECC and ICV errors #22431
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vogelpi
force-pushed
the
flash-ctrl-alert-fix
branch
2 times, most recently
from
April 4, 2024 16:48
c3ce236
to
7dd8304
Compare
@matutem I've triggered a full DV regression locally and will report back once I have the results. |
vogelpi
force-pushed
the
flash-ctrl-alert-fix
branch
from
April 4, 2024 20:51
7dd8304
to
6d10d02
Compare
The results are here:
|
Before, these two errors types led to a fatal alert which is problematic during firmware selection and verification. This commit changes the design in the following way: - The two relevant bits in the FAULT_STATUS CSR are made clearable by software. Other bits in this register remain sticky. - The corresponding alert is no longer fatal. This means the alert is only sent out until the two bits are cleared by software. To be on the safe side, firmware can still classify the alert as fatal on the receiver side (in the alert handler). For the other error sources, the alert keeps getting triggered as before, i.e., it remains fatal. For more background information, refer to lowRISC#21353. This resolves lowRISC#21637. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
force-pushed
the
flash-ctrl-alert-fix
branch
from
April 5, 2024 21:11
6d10d02
to
eda0e60
Compare
matutem
approved these changes
Apr 15, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before, these two errors types led to a fatal alert which is problematic during firmware selection and verification. This commit changes the design in the following way:
This means the alert is only sent out until the two bits are cleared by software. To be on the safe side, firmware can still classify the alert as fatal on the receiver side (in the alert handler). For the other error sources, the alert keeps getting triggered as before, i.e., it remains fatal.
For more background information, refer to #21353.
This resolves #21637.